Hello, I use Exchange 2007 and I have had a situation where I deactivate 1000 users (mailuser) through the MSC !! I did reactivate those users in no time and was able to handle the situation. However I have lost all smtp email addresses who users might use... Any my bigest problem right now is that Users (mailbox) using Oulook in cache mode are getting error message when creating/sending email to some of those users: IMCEAEX-_O=COMPANY_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28PLDPIOHF224PDLT+29_CN=RECIPIENTS_CN=USE@company.com #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ## I did add X500 Address: /o=Company/ou=Exchange Administrative Group (PLDPIOHF224PDLT)/cn=Recipients/cn=USE@company.com However, I still face the error (NDR). I wonder whether it is just matter of time until ost file and oab file will be updated on users machine or if I need to turn my investigation in another direction?? Any help would be more than appreciated. Note that sending new email from OWA do work just fine ! Many thanks in advance. Graig

Deactivating and reactivating an email account causes the Exchange internal routing for that user to change. what is causing the NDR is the cached email address popup, when a user starts typing an email address in the "To:" field in outlook (thats why its not happening in OWA), as it has the old route associated with that email address. We have this problem when we resurrect a previously removed email account. If they select the address from the GAL they shouldnt have the problem (assuming the GAL has been updated). You can have your users delete the email addresses in that drop down list or just you can just remove their N2K files for them. The N2K file is what stores all of those cached email addresses. In vista\win7 the n2k files is located at C:\Users\username\AppData\Roaming\Microsoft\Outlook\profilename.n2k. You will need to restart Outlook after you remove the file, i believe.dave

Thanks Dave. I have 600 accounts and it will be a pain in the neck to go through all of them. Is there any other possibility to fix that issue on the server side? I thought X500 address would be enough. In fact it fixed some accounts.. I get very confused about that cached mode. If I send an email from my outlook interface without the cahed mode active I have no NDR! When using cached mode it uses local files that should be updated at some stage no ?? Thanks, Graig

When you recreate the account, even with the same alias, internal Exchange sees it as a new email address (from what i can tell), I don't know if there is a way to restore it back to its old "address". I just tried it here, and it looks like switching from cached mode to online mode, changes which saved address index it looks at (ie when i was in cached mode, the removed\re-added email address showed up in my list, and NDR'ed when i sent to it, but when i switched to online mode, it was no longer there). Everything points back to that N2K, so i hope you can find a way to revert back to the old email routes!dave

It's easy to fix, when you de-provisoning any mail enabled contacts you loose the mail enabled properties, this includes legacydn and any custom x500 addresses like your case. You need to bulk add them which works in 90% of the cases except in some cases you might have accounts using non conventional format, those you just have to fix manually. The first thing you need to do is determine what the legacydn convention was for example o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=james chong Download admodify from codeplex to bulk modify. Test only on a single account after you have determined that the legacydn convention is correct. To test you can actually email the legacydn directly by putting in into the to: field in a new email message. 1. Admodify, modify attributes, 2. Select domain in drop down, select domain controller, click green arrow 3. highlight domain and click add to list. Note you can filter just on specific ou as well 4. select all next, 5. click custom tab Check make customized attribute modification Attribute name = proxyAddresses Attribute value = X500:/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=%'mailnickname'% Make sure you check multivalued append so it ADDs this additional address otherwise it whacks all proxy addresses and just adds this. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Thanks James. It seems like things are better now... I have updated: Get-EmailAddressPolicy | Update-EmailAddressPolicy Get-AddressList | Update-AddressList Get-GlobalAddressList | Update-GlobalAddressList And only wait 48h as it is the amount of hours that it would roughly take to have the *.oab and*.ost updated on local users computer. Thanks to everyone Graig

Can I ask whether it is describe somwhere that no Roll Back is possible when running a bad shell command (error that happened to me). Thanks, Graig